Skip to content

Conversation

bradzacher
Copy link
Contributor

I noticed that there was a schema defining an empty object - it's an unnecessary definition, so remove it.

schema: [{
type: 'object',
properties: {},
additionalProperties: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like it'd be a breaking change, in case someone had already been providing an empty object - also, the purpose of this schema is to make it easy for people to add new properties (without being forced to suddenly add the object)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as per #2341 - it's breaking in the strictest sense.

I personally don't see the point in keeping an invalid schema in here. Keeping it for the just in case seems a bit silly, considering that it has been waiting for just in case for 3 years?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major Breaking change.
Development

Successfully merging this pull request may close these issues.

2 participants